Skip to content

Tighten the AI guidelines and rules for new contributors - #1956

Open
picnixz wants to merge 1 commit into
python:mainfrom
picnixz:ai-policy-new-contributors
Open

picnixz wants to merge 1 commit into
python:mainfrom
picnixz:ai-policy-new-contributors

Conversation

@picnixz

@picnixz picnixz commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

First draft of a stricter AI policy for newcomers. Like the other PR, I also used Opus 5.5 for the text and reading the existing parts of the devguide and to polish the tone in a more... diplomatic way I would have said.

I think it grasps my main intent at least: we want newcomers to learn something, not to farm contribution points.

@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 CPython devguide | 🛠️ Build #35547177 | 📁 Comparing 90417ff against latest (a4da558)

  🔍 Preview build  

2 files changed
± getting-started/ai-tools/index.html
± triage/triage-team/index.html


.. _ai-tools-new-contributors:

Additional rules for new contributors

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't these rules apply to all contributors?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to allow "regular" contributors use of AI because of the trust they built, even if they are neither triagers nor core devs. But I don't want that the first contributions of users is solely AI. But if you want a stronger policy where this applies to everyone, I'm fine as well, though I think it's sad that core devs can't use what the AI generated for them.

It's hard to convene that but informally:

  • Newcomers: please don't use AI, you need to prove yourself.
  • Others: we can trust your judgment more so you also generate your PRs with AI. But please, make it so that it's not annoying to read.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants